| Package | ForgePatientChart.0830 |
| Type | StructureDefinition |
| Id | Id |
| FHIR Version | R4 |
| Source | https://simplifier.net/resolve?scope=ForgePatientChart.0830@0.1.0&canonical=https://telus.com/fhir/patientChart/StructureDefinition/profile-questionnaire |
| Url | https://telus.com/fhir/patientChart/StructureDefinition/profile-questionnaire |
| Status | draft |
| Name | Questionnaire |
| Experimental | False |
| Authority | hl7 |
| Description | This is created/used by the RAPIDS project within TELUS. May also have use within the Patient Chart project |
| Type | Questionnaire |
| Kind | resource |
No resources found
No resources found
FHIR{
"resourceType" : "StructureDefinition",
"url" : "https://telus.com/fhir/patientChart/StructureDefinition/profile-questionnaire",
"name" : "Questionnaire",
"status" : "draft",
"description" : "This is created/used by the RAPIDS project within TELUS. May also have use within the Patient Chart project",
"fhirVersion" : "4.0.1",
"kind" : "resource",
"abstract" : false,
"type" : "Questionnaire",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Questionnaire",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Questionnaire.id",
"path" : "Questionnaire.id",
"mustSupport" : true
},
{
"id" : "Questionnaire.identifier",
"path" : "Questionnaire.identifier",
"mustSupport" : true
},
{
"id" : "Questionnaire.version",
"path" : "Questionnaire.version",
"mustSupport" : true
},
{
"id" : "Questionnaire.name",
"path" : "Questionnaire.name",
"mustSupport" : true
},
{
"id" : "Questionnaire.title",
"path" : "Questionnaire.title",
"mustSupport" : true
},
{
"id" : "Questionnaire.status",
"path" : "Questionnaire.status",
"mustSupport" : true
},
{
"id" : "Questionnaire.publisher",
"path" : "Questionnaire.publisher",
"comment" : "Usage: If the publisher is known, this can be included, eg MMSE, MOCA\r\n\r\nUsually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.",
"mustSupport" : true
},
{
"id" : "Questionnaire.description",
"path" : "Questionnaire.description",
"comment" : "Usage Note: If present, this can be populated. PSS has a text area in the custom form that may map here. Other EMRs may also have this\r\n\r\nThis description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).",
"mustSupport" : true
},
{
"id" : "Questionnaire.code",
"path" : "Questionnaire.code",
"comment" : "Usage Note: This can be used to capture a LOINC code to represent the questionnaire, eg PHQ-9\r\n\r\nCodes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.",
"mustSupport" : true
},
{
"id" : "Questionnaire.code.system",
"path" : "Questionnaire.code.system",
"mustSupport" : true
},
{
"id" : "Questionnaire.code.code",
"path" : "Questionnaire.code.code",
"mustSupport" : true
},
{
"id" : "Questionnaire.code.display",
"path" : "Questionnaire.code.display",
"mustSupport" : true
},
{
"id" : "Questionnaire.item",
"path" : "Questionnaire.item",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Questionnaire.item.linkId",
"path" : "Questionnaire.item.linkId",
"comment" : "Usage Note: A LOINC code should be used if it exists; otherwise create a GUID. eg for PHQ-9, each question has a LOINC code;. For other custom questionnaires this can be structured in any logical way. Example: Custom Form Name + version + field identifier/field name. \r\n\r\nThis ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning. GUIDs or sequential numbers are appropriate here.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.definition",
"path" : "Questionnaire.item.definition",
"comment" : "Usage: If this is tied to a data dictionary, this can be referenced. This is not relevant to porting across and therefore will not be used.\r\n\r\nThe uri refers to an ElementDefinition in a [StructureDefinition](structuredefinition.html#) and always starts with the [canonical URL](references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition."
},
{
"id" : "Questionnaire.item.code",
"path" : "Questionnaire.item.code",
"comment" : "Usage note: This should be populated with a LOINC code if it exists.\r\n\r\nThe value may come from the ElementDefinition referred to by .definition.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.prefix",
"path" : "Questionnaire.item.prefix",
"comment" : "Usage Note: If this exists on a given form this may be populated.\r\n\r\nThese are generally unique within a questionnaire, though this is not guaranteed. Some questionnaires may have multiple questions with the same label with logic to control which gets exposed. Typically, these won't be used for \"display\" items, though such use is not prohibited. Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.text",
"path" : "Questionnaire.item.text",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Questionnaire.item.type",
"path" : "Questionnaire.item.type",
"comment" : "Usage note: Every widget in the template maps to one of these choices.\r\n\r\nAdditional constraints on the type of answer can be conveyed by extensions. The value may come from the ElementDefinition referred to by .definition.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.enableWhen",
"path" : "Questionnaire.item.enableWhen",
"comment" : "Usage Note: This may be difficult to extract from the template. For simple data structures this should be conveyed. \r\nUse case: This is valuable when migrating data from one EMR to another or when transferring a patient from one EMR to another.\r\n*See HL7 extensions for questionnaires\r\n\r\nIf multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true. I.e. treat \"enableWhen\"s as being joined by an \"or\" clause. This element is a modifier because if enableWhen is present for an item, \"required\" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enablic might evaluate to.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.enableBehavior",
"path" : "Questionnaire.item.enableBehavior",
"comment" : "Use case: This is valuable when migrating data from one EMR to another or when transferring a patient from one EMR to another.\r\n\r\nelement must be specified if more than one enableWhen value is provided.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.required",
"path" : "Questionnaire.item.required",
"comment" : "Usage note: This applies to all use cases as there is some clinical value in knowing this, though its primary value is the migration use case.\r\n\r\nQuestionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true. If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.repeats",
"path" : "Questionnaire.item.repeats",
"comment" : "Use case: This is valuable when migrating data from one EMR to another or when transferring a patient from one EMR to another.\r\nUsage Note: If you are dealing with a group (repetition for each family member), this repeats for each relative. If you are allowed to pick one answer, repeats = false, if you are allowed to pick more than one, repeates = true\r\n\r\nIf a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse. When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. \"repeat the question\") or to simply allow entry/selection of multiple answers for the question (repeat the answers). Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.\n\nThe resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.\n\n The value may come from the ElementDefinition referred to by .definition.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.readOnly",
"path" : "Questionnaire.item.readOnly",
"comment" : "Use Case: This would apply to all use cases and should be populated when this is \"true\" only. A value of \"false\" is not required.\r\n\r\nThe value of readOnly elements can be established by asserting extensions for defaultValues, linkages that support pre-population and/or extensions that support calculation based on other answers.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.maxLength",
"path" : "Questionnaire.item.maxLength",
"comment" : "Use case: This is valuable when migrating data from one EMR to another or when transferring a patient from one EMR to another.\r\n\r\nFor base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.answerValueSet",
"path" : "Questionnaire.item.answerValueSet",
"comment" : "Usage Note: This could be used when migrating data from one EMR to another or when transferring a patient from one EMR to another, however this requires a fairly deep level of sophistication and will therefore not be used at this time. The real value comes from template maintenance.\r\n\r\nUsage Note: This is useful when defining a value set and pointing to that, rather than including all possible answers. If there is a value set, this can be included here. Terminology will need to be published as an external value set, or it could be contained within this resource, or you can define all answer options, in which case you do not need this data element.\r\n\r\nLOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](loinc.html#alist). The value may come from the ElementDefinition referred to by .definition."
},
{
"id" : "Questionnaire.item.answerOption",
"path" : "Questionnaire.item.answerOption",
"comment" : "Use case: This is valuable when migrating data from one EMR to another or when transferring a patient from one EMR to another as we can transfer templates.\r\n\r\nThis element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.answerOption.value[x]",
"path" : "Questionnaire.item.answerOption.value[x]",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.answerOption.initialSelected",
"path" : "Questionnaire.item.answerOption.initialSelected",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.initial",
"path" : "Questionnaire.item.initial",
"comment" : "Usage Note: This is setting the default value for your question \r\nUse Case: The primary value is migrating templates from one EMR to another. \r\n\r\nSee HL7 extension for Initial Exptression. http://build.fhir.org/ig/HL7/sdc/StructureDefinition-sdc-questionnaire-initialExpression.html\r\n\r\nThe user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created. Note that initial values can influence results. The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.initial.value[x]",
"path" : "Questionnaire.item.initial.value[x]",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.item",
"path" : "Questionnaire.item.item",
"comment" : "Usage Note: For nested items, the same rules apply as for Questionnarire.item \r\n\r\nThere is no specified limit to the depth of nesting. However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.",
"contentReference" : "http://hl7.org/fhir/StructureDefinition/Questionnaire#Questionnaire.item",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.item.linkId",
"path" : "Questionnaire.item.item.linkId",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.item.code",
"path" : "Questionnaire.item.item.code",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.item.prefix",
"path" : "Questionnaire.item.item.prefix",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.item.text",
"path" : "Questionnaire.item.item.text",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.item.type",
"path" : "Questionnaire.item.item.type",
"mustSupport" : true
},
{
"id" : "Questionnaire.item.item.item",
"path" : "Questionnaire.item.item.item",
"contentReference" : "http://hl7.org/fhir/StructureDefinition/Questionnaire#Questionnaire.item",
"mustSupport" : true
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.